NTISthis.com

Evidence Guide: ICTPRG401 - Maintain open-source code programs

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG401 - Maintain open-source code programs

What evidence can you provide to prove your understanding of each of the following citeria?

Investigate the open-source paradigm

  1. Examine the open-source paradigm and analyse the differences with traditional software development models
  2. Investigate the types of online resources
  3. Investigate the types of project documentation
  4. Recognise the role of an online community, and international collaboration
  5. Examine motivational factors for contributors to open-source code
  6. Analyse the open-source licensing models
Examine the open-source paradigm and analyse the differences with traditional software development models

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Investigate the types of online resources

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Investigate the types of project documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Recognise the role of an online community, and international collaboration

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine motivational factors for contributors to open-source code

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the open-source licensing models

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Familiarise with target project

  1. Examine the online resources associated with the target project
  2. Download pre-built executable binaries to install, and run, the project
  3. Download and analyse the supporting documentation
Examine the online resources associated with the target project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Download pre-built executable binaries to install, and run, the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Download and analyse the supporting documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare for maintenance activities

  1. Select, and register with, a relevant online community open-source group
  2. Download nightly snapshots of the latest source code and the supporting documentation
  3. Build and execute a snapshot, where appropriate
Select, and register with, a relevant online community open-source group

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Download nightly snapshots of the latest source code and the supporting documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build and execute a snapshot, where appropriate

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Maintain the code

  1. Access the project bug database, and select the bugs to be resolved or the features to be added
  2. Make changes to the local copy of the code, in order to resolve selected bugs
  3. Test the resulting code to ensure that it performs appropriately
  4. Prepare the code patch for submission
  5. Submit a code patch to the project
  6. Use the appropriate software-development tools and environment
Access the project bug database, and select the bugs to be resolved or the features to be added

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Make changes to the local copy of the code, in order to resolve selected bugs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test the resulting code to ensure that it performs appropriately

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare the code patch for submission

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit a code patch to the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Use the appropriate software-development tools and environment

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Maintain the documentation

  1. Access the project documentation
  2. Prepare and contribute new information, or updates, to the existing documentation
  3. Prepare and submit documented changes to the project
Access the project documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare and contribute new information, or updates, to the existing documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare and submit documented changes to the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Participate in community

  1. Exchange messages with other project members and actively participate in community activities
  2. Take action to ensure that exchanges are socially acceptable
  3. Submit the code and documentation code patches for inclusion
  4. Access online project resources frequently, to keep up-to-date with the project and with community developments
  5. Take action to ensure that community-participation standards are observed and maintained
Exchange messages with other project members and actively participate in community activities

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that exchanges are socially acceptable

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit the code and documentation code patches for inclusion

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Access online project resources frequently, to keep up-to-date with the project and with community developments

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that community-participation standards are observed and maintained

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Investigate the open-source paradigm

1.1 Examine the open-source paradigm and analyse the differences with traditional software development models

1.2 Investigate the types of online resources

1.3 Investigate the types of project documentation

1.4 Recognise the role of an online community, and international collaboration

1.5 Examine motivational factors for contributors to open-source code

1.6 Analyse the open-source licensing models

2. Familiarise with target project

2.1 Examine the online resources associated with the target project

2.2 Download pre-built executable binaries to install, and run, the project

2.3 Download and analyse the supporting documentation

3. Prepare for maintenance activities

3.1 Select, and register with, a relevant online community open-source group

3.2 Download nightly snapshots of the latest source code and the supporting documentation

3.3 Build and execute a snapshot, where appropriate

4. Maintain the code

4.1 Access the project bug database, and select the bugs to be resolved or the features to be added

4.2 Make changes to the local copy of the code, in order to resolve selected bugs

4.3 Test the resulting code to ensure that it performs appropriately

4.4 Prepare the code patch for submission

4.5 Submit a code patch to the project

4.6 Use the appropriate software-development tools and environment

5. Maintain the documentation

5.1 Access the project documentation

5.2 Prepare and contribute new information, or updates, to the existing documentation

5.3 Prepare and submit documented changes to the project

6. Participate in community

6.1 Exchange messages with other project members and actively participate in community activities

6.2 Take action to ensure that exchanges are socially acceptable

6.3 Submit the code and documentation code patches for inclusion

6.4 Access online project resources frequently, to keep up-to-date with the project and with community developments

6.5 Take action to ensure that community-participation standards are observed and maintained

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Investigate the open-source paradigm

1.1 Examine the open-source paradigm and analyse the differences with traditional software development models

1.2 Investigate the types of online resources

1.3 Investigate the types of project documentation

1.4 Recognise the role of an online community, and international collaboration

1.5 Examine motivational factors for contributors to open-source code

1.6 Analyse the open-source licensing models

2. Familiarise with target project

2.1 Examine the online resources associated with the target project

2.2 Download pre-built executable binaries to install, and run, the project

2.3 Download and analyse the supporting documentation

3. Prepare for maintenance activities

3.1 Select, and register with, a relevant online community open-source group

3.2 Download nightly snapshots of the latest source code and the supporting documentation

3.3 Build and execute a snapshot, where appropriate

4. Maintain the code

4.1 Access the project bug database, and select the bugs to be resolved or the features to be added

4.2 Make changes to the local copy of the code, in order to resolve selected bugs

4.3 Test the resulting code to ensure that it performs appropriately

4.4 Prepare the code patch for submission

4.5 Submit a code patch to the project

4.6 Use the appropriate software-development tools and environment

5. Maintain the documentation

5.1 Access the project documentation

5.2 Prepare and contribute new information, or updates, to the existing documentation

5.3 Prepare and submit documented changes to the project

6. Participate in community

6.1 Exchange messages with other project members and actively participate in community activities

6.2 Take action to ensure that exchanges are socially acceptable

6.3 Submit the code and documentation code patches for inclusion

6.4 Access online project resources frequently, to keep up-to-date with the project and with community developments

6.5 Take action to ensure that community-participation standards are observed and maintained

Evidence of the ability to:

contribute to an open-source project

program source code changes and/or additions

document changes or additions

investigate, utilise and participate in online resources for the project’s direction

build, modify, and test the code

participate in the online community.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain debugging and testing techniques

describe documentation techniques, including internal documentation, user guides and technical documentation

explain open-source development methodology

describe online project communities, and their involvement in games development.